<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
	<TITLE></TITLE>
	<META NAME="GENERATOR" CONTENT="OpenOffice.org 2.2  (Win32)">
	<META NAME="AUTHOR" CONTENT="L Ward">
	<META NAME="CREATED" CONTENT="20091203;16001772">
	<META NAME="CHANGED" CONTENT="20091206;11101970">
	<STYLE TYPE="text/css">
	<!--
		@page { size: 8.5in 11in; margin: 0.79in }
		P { margin-bottom: 0.08in }
	-->
	</STYLE>
</HEAD>
<BODY LANG="en-US" DIR="LTR">
<P STYLE="margin-bottom: 0in"><B>Testing Process Overview</B></P>
<P STYLE="margin-bottom: 0in"><BR>
</P>
<P STYLE="margin-bottom: 0in"><I><B>Manager Tasks</B></I></P>
<P STYLE="margin-bottom: 0in; font-style: normal; font-weight: medium">
<A HREF="Administering_Users.html">Creating users</A> &ndash; Users
are generally created at the time of installation and should only
change when testers leave or join the company.</P>
<P STYLE="margin-bottom: 0in; font-style: normal; font-weight: medium">
<A HREF="Administering_Releases.html">Creating releases</A> &ndash;
Releases should ideally be created in advance, at the beginning of
year, when the release schedule is created. If this is not known,
releases can be created at any time, but must be created before test
plans can be created.</P>
<P STYLE="margin-bottom: 0in; font-style: normal; font-weight: medium">
<A HREF="Administering_Environments.html">Creating environments</A> &ndash;
Environments generally do not change and should be created at the
time of installation. Some examples may be a Test, Staging and
Production environment. If the software being tested is desktop
software, environments for Windows XP, Vista, Linux etc. may be
created.</P>
<P STYLE="margin-bottom: 0in"><BR>
</P>
<P STYLE="margin-bottom: 0in"><I><B>Tester Tasks</B></I></P>
<P STYLE="margin-bottom: 0in; font-style: normal; font-weight: medium">
<A HREF="Creating_Test_Plans.html">Creating test plans</A> &ndash;
Once the software being developed is ready for quality assurance, a
test plan will be created to detail the tests that will be run to
ensure that it functions properly. This plan will be created under a
release that the manager should have created previously. Other
projects may use the same release.</P>
<P STYLE="margin-bottom: 0in; font-style: normal; font-weight: medium">
<A HREF="Creating_Test_Cases.html">Creating test cases</A> &ndash;
Test cases can be created at any time during the testing process.
Test cases may be added or removed from the test plan to adjust to
changing requirements for the software or changes in the depth of
testing that is necessary. Even after execution, test cases may be
added or removed. Generally speaking, however, the entire test plan
should be complete before any test cases are executed.</P>
<P STYLE="margin-bottom: 0in; font-style: normal; font-weight: medium">
<A HREF="Executing_Test_Cases.html">Executing test cases</A> &ndash;
To store the results of test cases, such as whether the test was
successful (passed) or unsuccessful (failed), cases must be executed.
This task is the primary driver for determining the status of a
particular plan or release via the reporting software.</P>
<P STYLE="margin-bottom: 0in; font-style: normal; font-weight: medium">
<BR>
</P>
<P STYLE="margin-bottom: 0in; font-style: normal; font-weight: medium">
<BR>
</P>
<P STYLE="margin-bottom: 0in"><BR>
</P>
</BODY>
</HTML>